fix: module-scoped data-dir to avoid loading stale monorepo index#51
Merged
aviadshiber merged 1 commit intomainfrom Apr 12, 2026
Merged
fix: module-scoped data-dir to avoid loading stale monorepo index#51aviadshiber merged 1 commit intomainfrom
aviadshiber merged 1 commit intomainfrom
Conversation
When jdtls starts scoped to a single module, use the module URI for the data-dir hash instead of the workspace root. This prevents loading a 2.5GB cached index from previous full-workspace sessions, which caused the initialize request to time out at 120s. Each module now gets its own small data-dir (~10-50MB), enabling fast cold starts (~10s) for on-demand module loading. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
aviadshiber
force-pushed
the
fix/module-scoped-data-dir
branch
from
c46d077 to
d2ef0d7
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Context
PR #50 removed eager workspace expansion but jdtls initialize still timed out at 120s because the data-dir was shared across all sessions. The products monorepo data-dir had grown to 2.5GB from previous full-workspace sessions. Even scoped to one module, jdtls loaded the entire cached state.
Test plan
🤖 Generated with Claude Code